SUPPORT / SAMPLES & SAS NOTES
 

Support

Installation Note 56960: SAS® Deployment Wizard might fail when you import the Shared Services database during configuration of the SAS® Web Infrastructure Platform under UNIX

DetailsHotfixAboutRate It

In the third maintenance release for SAS® 9.4 (TS1M3), configuration of the Web Infrastructure Platform might fail during a migration deployment. This problem occurs because of an error that is encountered when the Shared Services database is migrated. This failure only occurs when both of the following conditions occur:

  • SAS 9.4 TS1M3 is deployed in UNIX operating environments.
  • Different user accounts are used to run the SAS® Migration Utility, which creates the migration package on the source environment, and to run SAS® Deployment Wizard, which loads the migration package on the target environment.

When this problem occurs, the webinfpltfm_ImportDatabase.log file displays the following exception showing that there is an error with importing the database:

com.sas.smu.webinfpltfm.DbException: Exception encountered migrating database table: null . . .more message lines. . . Caused by: java.lang.IllegalArgumentException: A writable directory must be specified.

In addition, the webinfpltfm_startServer_yyyy-mm-dd-hh-mm-ss.log file indicates that the configuration failed:

BUILD FAILED /install/lrc_sovW33_migr/SASHome/SASWebInfrastructurePlatform/9.4/Config/webinfpltfm_config.xml:692: Java returned: 3 at org.apache.tools.ant.taskdefs.Java.execute(Java.java:107)

If you encounter this configuration failure and if SAS Deployment Wizard is still running, you can try the following workaround:

  1. Grant Write permission for SAS-Migration-Utility-package-directory/your-server-name/webinfpltfm to the user account that is running SAS Deployment Wizard.
  2. Delete the Shared Services database so that it will be re-created.
  3. Remove the following files and directories:
  4. .../Lev1/AppData/SASContentServer/Repository/repository .../Lev1/AppData/SASContentServer/Repository/workspaces .../Lev1/AppData/SASContentServer/Repository/.SCSOK .../Lev1/AppData/SASContentServer/Repository/.lock (if exists) .../Lev1/AppData/SASContentServer/Repository/revision.log (if exists)

    Note: DO NOT REMOVE the repository.xml file from the .../Lev1/AppData/SASContentServer/Repository/ directory.

  5. Click the Retry button in the deployment wizard.

However, you can circumvent the problem completely by using either of the following methods:

  • Rerun the migration configuration, ensuring that you run SAS Deployment Wizard on the target with the same user account that is used to create the SAS Migration Utility package on the source.
  • Before you run SAS Deployment Wizard, change ownership of the SAS-Migration-Utility-package-directory/ on the target environment to the new user account that is running the deployment wizard.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Enterprise BI Server64-bit Enabled AIX9.49.4_M49.4 TS1M39.4 TS1M4
64-bit Enabled Solaris9.49.4_M49.4 TS1M39.4 TS1M4
HP-UX IPF9.49.4_M49.4 TS1M39.4 TS1M4
Linux for x649.49.4_M49.4 TS1M39.4 TS1M4
Solaris for x649.49.4_M49.4 TS1M39.4 TS1M4
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.